Have alpine sorted the reason why we had to downgrade back to 3.13 last year?

If not have sufficient numbers of people upgraded their dockers to prevent it from being problem?

This should help with the issue described in #17994 related to old npm.

Let me be clearer:

Alpine 3.14+ will cause everyone using gitea with docker less than version 20.10.6 to break. (https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.14.0)

We upgraded to alpine 3.14 and had multiple bug reports like:

#16428, #16451, #16170, #16464, #16484

See:

https://about.gitlab.com/blog/2021/08/26/its-time-to-upgrade-docker-engine/

For when gitlab were finally bitten by this.

So the question is has enough of the docker community moved over to update their docker installs and have they been bitten elsewhere yet?

One option is to do this but also add a check in to Gitea that will check if this bug is present and report that we cannot run.

That's a lot of new information for me, too.

If we can write the background in comment, maybe new developers won't have questions anymore.

So looking at:

alpinelinux/docker-alpine#156 (comment) & alpinelinux/docker-alpine#156 (comment)

May provide techniques for us to test at time of docker run if things are going to be broken.

if [ ! -x /bin/bash ]; then echo "I should not get printed!"; fi

Directory test also failed ( test -x /tmp then echo $? , got 1 )

Docker is just a dependency in this case. We should document its minimum version and possible refuse to run if it's too old. Question is, can a container detect the version of the docker daemon it runs on?

Docker is just a dependency in this case. We should document its minimum version and possible refuse to run if it's too old. Question is, can a container detect the version of the docker daemon it runs on?

this might do it
cat /proc/self/cgroup | grep -o -e "docker-.*.scope" | head -n 1 | sed "s/docker-\(.*\).scope/\\1/"